System, method and computer program product for storing reports for use by tenants of a multi-tenant on-demand database service

ABSTRACT

In accordance with embodiments, there are provided mechanisms and methods for storing reports for use by tenants of a multi-tenant on-demand database service. These mechanisms and methods for storing reports for use by tenants of a multi-tenant on-demand database service may allow tenants of the multi-tenant on-demand database service to create, modify, etc. reports programmatically, as desired, and may allow the multi-tenant on-demand database service to make the reports accessible to other tenants of the multi-tenant on-demand database service.

CLAIM OF PRIORITY

This application claims the benefit of U.S. Provisional PatentApplication 61/096,554 entitled “Methods and Systems for ReportingMetaData at an On Demand Service,” by Wisnovsky et al., filed Sep. 12,2008, the entire contents of which are incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

The current invention relates generally to reports, and moreparticularly to storing reports.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also be inventions.

In conventional database systems, reports have generally been stored insuch databases utilizing proprietary formats. Unfortunately, variouslimitations exist as a result of storing reports in a proprietaryformat. In many cases, reports have been stored utilizing a formatproprietary to the service providing the database. Thus, developerswithout a specialized knowledge of development in the proprietary format(e.g. developers external to a provider of the database system) areoftentimes required to utilize a preconfigured user interface of thedatabase service for creating a report in the proprietary format.

In other cases, reports have been stored utilizing a format proprietaryto the developer creating the reports. Thus, reports in a format that isproprietary to a specific developer have generally been incapable ofbeing shared, distributed, etc. across other entities (e.g. users,organizations, etc.).

BRIEF SUMMARY

In accordance with embodiments, there are provided mechanisms andmethods for storing reports for use by tenants of a multi-tenanton-demand database service. These mechanisms and methods for storingreports for use by tenants of a multi-tenant on-demand database servicemay allow tenants of the multi-tenant on-demand database service tocreate, modify, etc. reports programmatically, as desired, and may allowthe multi-tenant on-demand database service to make the reportsaccessible to other tenants of the multi-tenant on-demand databaseservice.

In an embodiment and by way of example, a method is provided for storingreports for use by tenants of a multi-tenant on-demand database service.In use, a report is received from a first tenant of a multi-tenanton-demand database service. Further, the report is stored for use by atleast one second tenant of the multi-tenant on-demand database service.

While the present invention is described with reference to an embodimentin which techniques storing reports for use by tenants of a multi-tenanton-demand database service are implemented in an application serverproviding a front end for the multi-tenant database on-demand service,the present invention is not limited to multi-tenant databases ordeployment on application servers. Embodiments may be practiced usingother database architectures, i.e., ORACLE®, DB2® and the like withoutdeparting from the scope of the embodiments claimed.

Any of the above embodiments may be used alone or together with oneanother in any combination. Inventions encompassed within thisspecification may also include embodiments that are only partiallymentioned or alluded to or are not mentioned or alluded to at all inthis brief summary or in the abstract. Although various embodiments ofthe invention may have been motivated by various deficiencies with theprior art, which may be discussed or alluded to in one or more places inthe specification, the embodiments of the invention do not necessarilyaddress any of these deficiencies. In other words, different embodimentsof the invention may address different deficiencies that may bediscussed in the specification. Some embodiments may only partiallyaddress some deficiencies or just one deficiency that may be discussedin the specification, and some embodiments may not address any of thesedeficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a method for storing reports for use by tenants of amulti-tenant on-demand database service, in accordance with oneembodiment.

FIG. 2 shows a method for provisioning reports stored using amulti-tenant on-demand database service to tenants of the multi-tenanton-demand database service, in accordance with another embodiment.

FIG. 3 shows a user interface for configuring filters for a report, inaccordance with yet another embodiment.

FIG. 4 shows a user interface for grouping reports, in accordance withstill yet another embodiment.

FIG. 5 illustrates a block diagram of an example of an environmentwherein an on-demand database service might be used.

FIG. 6 illustrates a block diagram of an embodiment of elements of FIG.5 and various possible interconnections between these elements.

DETAILED DESCRIPTION

General Overview

Systems and methods are provided for storing reports for use by tenantsof a multi-tenant on-demand database service.

To date, conventional database systems have required reports to bestored in such databases utilizing proprietary formats. Unfortunately,various limitations exist as a result of storing reports in aproprietary format. Thus, mechanisms and methods are provided herein forstoring reports for use by tenants of a multi-tenant on-demand databaseservice to allow tenants of the multi-tenant on-demand database serviceto create, modify, etc. reports programmatically, as desired, and toallow the multi-tenant on-demand database service to make the reportsaccessible to other tenants of the multi-tenant on-demand databaseservice.

Next, mechanisms and methods for storing reports for use by tenants of amulti-tenant on-demand database service will be described with referenceto exemplary embodiments.

FIG. 1 shows a method 100 for storing reports for use by tenants of amulti-tenant on-demand database service, in accordance with oneembodiment. As shown, a report is received from a first tenant of amulti-tenant on-demand database service. See operation 102.

In the context of the present description, the report may include anaccounting, summarization, representation, evaluation, etc. of any typeof data that is capable of being received from the first tenant of themulti-tenant on-demand database service. For example, the report maysummarize financial information, product and/or service information,entity (e.g. user, organization, etc.) information, etc. In oneexemplary embodiment, the report may include a table (e.g. of columnsand rows defining a plurality of cells). It should be noted that thereport may be of a predetermined type (e.g. defined based on apredetermined template) or may be entirely customized.

Additionally, the report may include a plurality of portions (e.g.attributes), for example, defined by the first tenant of themulti-tenant on-demand database service. Thus, report may be created bythe first tenant of the multi-tenant on-demand database service based onthe defined portions.

In one embodiment, the portions of the report may include columns (e.g.displayed in the report). For example, the report may include a tableand the columns may include columns of the table. As another example,the columns may each be defined (e.g. by the first tenant) to include adifferent type of data. As yet another example, the columns may definean ordering associated with the report.

In another embodiment, the portions of the report may include filters(e.g. applied to data being reported via the report). Each filter mayoptionally be defined by a filter item. For example, the filter item mayinclude an identifier of a column to which the filter is applied, anoperator, and a value against which the column is applied based on theoperator.

In yet another embodiment, the portions of the report may include ascope of data reported via the report. For example, the scope mayindicate a subset of data being reported via the report (to which thefilters are applied, etc.). The subset of data may include a subset ofdata in a particular database (e.g. of the multi-tenant on-demanddatabase service), such as data for a particular tenant of themulti-tenant on-demand database service, data for a particular accountof a particular tenant of the multi-tenant on-demand database service,etc.

In still yet another embodiment, the portions of the report may includeformulas. The formulas may each apply at least one function to data,such that a result of the application of the function to the data may beincluded in the report. For example, the formulas may apply mathematicaloperations (e.g. sum, etc.) to data.

In a further embodiment, the portions of the report may includegroupings. The groupings may each include a group of rows and/or columnsof data to include in the report (e.g. summarized in the report, etc.).For example, a summarization of data indicated by the grouping may beprovided in the report.

In another embodiment, the portions of the report may includeparameters. The parameters may be specific to the report. Just by way ofexample, the parameters may include a set of values specific to thereport. As another example, the parameters may be associated withspecific options, user interface elements, etc. that are available formodifying the report.

The portions of the report may also include color ranges. The colorranges may each indicate a color coding of data (e.g. cells, etc.) ofthe report. For example, a plurality of ranges may each be specifiedwith a different color, such that data in the report that is within oneof the ranges may be color coded according to the color specified forthat range.

It should be noted that the portions of the report may be defined by thefirst tenant of the multi-tenant on-demand database service in anydesired manner. As an option, the portions of the report may be definedby the first tenant utilizing a user interface [e.g. a graphical userinterface (GUI)] of the multi-tenant on-demand database service. Theuser interface may include various options (e.g. fields, etc.) forallowing the first tenant to configure columns, filters, parameters,etc. of the report.

As another option, the portions of the report may be definedprogrammatically (e.g. without use of the user interface of the metadataschema may include) by the first tenant utilizing a metadata schema. Themetadata schema may include a human-readable schema (e.g. non-encoded,etc.). Just by way of example, the metadata schema may include anextensible markup language (XML) schema.

As noted above, the report is received from the first tenant of themulti-tenant on-demand database service. In the present description,such multi-tenant on-demand database service may include any servicethat relies on a database system that is accessible over a network, inwhich various elements of hardware and software of the database systemmay be shared by one or more tenants (e.g. customers, organizations,groups, users, etc.). For instance, a given application server maysimultaneously process requests for a great number of customers, and agiven database table may store rows for a potentially much greaternumber of customers. Various examples of such a multi-tenant on-demanddatabase service will be set forth in the context of differentembodiments that will be described during reference to subsequentfigures.

In one embodiment, the report may be received by the multi-tenanton-demand database service. For example, the report may be received bythe multi-tenant on-demand database service utilizing an applicationprogram interface (API) of the multi-tenant on-demand database service.Optionally, the report may be received over a network from a device(e.g. computer, etc.) of the first tenant. As another option, the reportmay be received in association with a request from the first tenant tostore the report.

Furthermore, as shown in operation 104, the report is stored for use byat least one second tenant of the multi-tenant on-demand databaseservice. In one embodiment, the second tenant may include a tenant ofthe multi-tenant on-demand database service that is different than thefirst tenant of the multi-tenant on-demand database service. To thisend, the report may be received from the first tenant and stored for use(e.g. viewing, modifying, purchasing, etc.) thereof by any othertenant(s) of the multi-tenant on-demand database service.

In one embodiment, the report may be stored in a database of themulti-tenant on-demand database service. Accordingly, the second tenantmay access the report for use thereof via an API of the multi-tenanton-demand database service. Of course, however, the report may be storedin any desired location which allows use thereof by the second tenant ofthe multi-tenant on-demand database service.

Moreover, the report may be stored in any desired format which allowsuse thereof by the second tenant of the multi-tenant on-demand databaseservice. For example, the report may be stored in a format accessible tothe first tenant and the second tenant. Thus, the report may be storedin a format that is non-proprietary with respect to the tenants of themulti-tenant on-demand database service and the multi-tenant on-demanddatabase service itself.

As an option, the report may be stored utilizing the metadata schemadescribed above with respect to operation 102. For example, the reportmay be defined by the first tenant utilizing the metadata schema, andthe report may be stored in such metadata schema format. The metadataschema may include a schema that is usable (e.g. readable,non-proprietary, etc.) by the second tenant of the multi-tenanton-demand database service, such that the report may be stored in aformat usable by other tenants of the multi-tenant on-demand databaseservice.

As another example, the report may be defined by the first tenantutilizing the user interface of the multi-tenant on-demand databaseservice (described above). Further, the report may be converted from aformat associated with the user interface to the metadata schema forstorage of the report in the metadata schema format. In this way, thereport may be stored in a format usable by other tenants of themulti-tenant on-demand database service even when the report is definedutilizing a user interface of the multi-tenant on-demand databaseservice.

FIG. 2 shows a method 200 for provisioning reports stored using amulti-tenant on-demand database service to tenants of the multi-tenanton-demand database service, in accordance with another embodiment. As anoption, the present method 200 may be carried out in the context of thefunctionality of FIG. 1. For example, the method 200 may be carried outby the multi-tenant on-demand database service. Of course, however, themethod 200 may be carried out in any desired environment. Theaforementioned definitions may apply during the present description.

As shown in decision 202, it is determined whether a report is receivedfrom a first tenant of a multi-tenant on-demand database service. In oneembodiment, the determination may include determining whether a reporthas been received by an API of the multi-tenant on-demand databaseservice. In another embodiment, the determination may includedetermining whether a request to store the report, where the requestincludes the report, has been received from the first tenant (e.g. atthe API of the multi-tenant on-demand database service). If it isdetermined that the report is not received, the method 200 continues towait for a report to be received from the first tenant.

With respect to the description of the present embodiment, the reportmay be defined (e.g. created) by the first tenant. For example, thefirst tenant may define the report by defining various portions of thereport. The portions may include a type of the report, columns of thereport, etc., as described below.

In one embodiment, a type of the report may be defined. The type of thereport may include one of a plurality of predefined types (e.g. reporttemplates, etc.), for example. As an option, the type may indicateinformation that is available for use in defining the report, such asobjects available to the report (e.g. which subset of data may bereported via the report, columns available to be reported, parametersthat may be used in the report, etc.), columns from the objects that areavailable to the report, parameters that are available to the report,etc. Of course, in another embodiment, the type of the report may notnecessarily be defined such that the report may be entirely customized(e.g. configured) by the first tenant.

Optionally, a description of the predefined types of reports may beprovided to the first tenant via a describe API of the multi-tenanton-demand database service. The describe API may present to the firsttenant the information that is available for use in defining the report.For example, a web service definition language method may enumerate thevarious report types (including predefined types and an entirelycustomized type) and may describe the information that is available foruse in defining each different type of report.

In another embodiment, a format of the report may be defined. The formatmay indicate whether the report is tabular, a summary, a matrix, etc.Additionally, the format may restrict the manner in which other portionsof the report may be defined. Just by way of example, only a tabularreport can specify a top predetermined number of options. As anotherexample, only summary and matrix reports may specify groupings and/orformulas (describe in more detail below).

In yet another embodiment, a scope of the report may be defined. Thescope may indicate the data that is available for reporting via thereport. For example, the scope may indicate a subset of data beingreported via the report. The subset of data may include a subset of datain a particular database (e.g. of the multi-tenant on-demand databaseservice), such as data for a particular tenant of the multi-tenanton-demand database service, data for a particular account of aparticular tenant of the multi-tenant on-demand database service, etc.

In still yet another embodiment, columns of the report may be defined.The columns may include those displayed via the report. As an option,the columns may define an ordering.

In a further embodiment, filters used in the report may be defined. Thedefined filters may include those applied to data being reported via thereport. Optionally, each filter may be defined by a filter itemincluding an identifier of a column to which the filter is applied, anoperator, and a value against which the column is applied based on theoperator. Multiple filter items may be defined for the report, in oneembodiment. In such embodiment, the multiple filter items may be ordered(based on the order in which the filter items are entered by the firsttenant), for identifying a sequence in which the filter items areapplied to data being reported via the report.

In another embodiment, groupings may be defined for the report. Thegroupings may be used to group columns and/or rows being reported viathe report. Just by way of example, date groupings may be used to groupdate columns. Optionally, the date grouping may allow a truncation levelfor the date (e.g. day, month, year, fiscal options which vary basedwhether the fiscal years utilized are standard or custom, etc.). Asanother option, the groupings may be ordered in the report.

Formulas for the report may also be defined, in one embodiment. Theformulas may each apply at least one function to data (e.g. data beingreported via the report), such that a result of the application of thefunction to the data may be included in the report. For example, theformulas may apply mathematical operations (e.g. sum, etc.) to data. Inthis way, the formulas may summarize the data based on operations in theformula (e.g. summing, etc.). Optionally, the formulas may only beutilized with respect to summary and/or matrix reports.

In yet another embodiment, parameters for the report may be defined. Theparameters (e.g. name/value pairs) may be specific to the type of reportdefined by the first tenant, as described above. Just by way of example,the parameters may include a set of values specific to the report. Asanother example, the parameters may be associated with specific options,user interface elements, etc. that are available for modifying thereport. In one exemplary embodiment, an activities type report may allowthe first tenant to specify whether open and/or closed activities, tasksand/or events, etc. are presented via the report.

Color ranges for the report may also be defined, in one embodiment. Thecolor ranges may each indicate a color coding of data (e.g. cells, etc.)of the report. For example, a plurality of ranges may each be specifiedwith a different color, such that data in the report that is within oneof the ranges may be color coded according to the color specified forthat range. In this way, summary and/or matrix cells that containaggregate values (e.g. based on an applied formula) within a particularrange may be highlighted using a color defined for that range.

As an option, the report may be validated prior to being used by othertenants of the multi-tenant on-demand database service (e.g. at runtime,etc.). Each validation may be common or different with respect toreports defined programmatically and via a user interface of themulti-tenant on-demand database service. For each portion of the reportthat is not validated, an error may be returned to the first tenant forcorrecting the invalidated report definition (e.g. only if the report isdefined programmatically). As another option, the invalidated portionsmay be automatically corrected (e.g. only if the report is defined viathe user interface).

In one embodiment, the validations may validate the format defined forthe report. For example, if a grouping or formula is added to a tabularreport via the user interface, the report may be automatically changedto a summary or matrix format, if all groupings are removed from asummary or matrix report, the report may be automatically changed to atabular format, etc. As another example, errors may be returned to thefirst tenant if a tabular report has any groupings or formulas defined,if a summary report does not define a grouping, if a matrix report doesnot define a column grouping and a row grouping, etc.

In another embodiment, the validations may validate the scope definedfor the report. For example, different scopes may be available todifferent types of reports. Thus, the validation may include validatingwhether the scope defined for the report is available for the definedtype of the report.

In yet another embodiment, the validations may validate filters definedfor the report. Optionally, a predefined subset of operators may only beavailable for use for being applied to particular columns of data. Thus,the validation may validate whether an operator included in a formulaapplied against a particular column is available for use with respect tothat column.

In still yet another embodiment, the parameters defined for the reportmay be validated. For example, parameters may be validated with respectto the defined type of the report (e.g. for validating that theparameters are available for the type of the report). Of course, whilevarious examples of validations have been described above, it should benoted that the report may be validated in any desired manner.

Table 1 shows one example of a report programmatically defined utilizingan XML schema. It should be noted that the report is set forth forillustrative purposes only, and thus should not be construed as limitingin any manner.

TABLE 1 <?xml version=“1.0” encoding=“UTF-8”?> <CustomReportxmlns=“http://soap.sforce.com/2006/04/metadata”> <chartXAxisColumn>INDUSTRY</chartXAxisColumn> <chartYAxisColumn>CLOSE_MONTH</chartYAxisColumn>  <columns>  <field>FULL_NAME</field>  </columns>  <columns>  <field>OPPORTUNITY_NAME</field>  </columns>  <columns>  <field>TYPE</field>  </columns>  <columns>   <field>AMOUNT</field> </columns>  <filters>   <column>AGE</column>  <operator>greaterThan</operator>   <value>0</value>  </filters> <format>Matrix</format>  <params>   <name>quarter</name>  <value>custom</value>  </params>  <params>   <name>scope</name>  <value>organization</value>  </params>  <params>   <name>open</name>  <value>all</value>  </params>  <params>   <name>probability</name>  <value>&gt;0</value>  </params>  <params>   <name>div_rep</name>  <value></value>  </params>  <reportType>Opportunity</reportType> <scope>organization</scope>  <showDetails>false</showDetails> <sortAsc>false</sortAsc> </CustomReport>

As shown in Table 1, the syntax used to define the report uses API namesfor each defined portion of the report. For example, the <table> tag mayidentify the table that a field in the report type in the report sitson. Further, the field tag may identify the field on the table thatdefines the report column. In the present example, both the table andthe field may be required to be defined in order to uniquely specify acolumn. Moreover, it should be noted that a table may appear multipletimes in one report type, as well as the fields on that table.

Table 2 illustrates one example of programmatically defined color rangesfor a report. Again, it should be noted that the programmaticallydefined color ranges are set forth for illustrative purposes only, andthus should not be construed as limiting in any manner.

TABLE 2 <colorRanges>  <aggregate>Sum</aggregate> <columnName>EXP_AMOUNT</columnName> <highBreakpoint>5000.0</highBreakpoint>  <highColor>   <blue>84</blue>  <green>194</green>   <red>84</red>  </highColor> <lowBreakpoint>100.0</lowBreakpoint>  <lowColor>   <blue>0</blue>  <green>204</green>   <red>51</red>  </lowColor>  <midColor>  <blue>84</blue>   <green>194</green>   <red>194</red>  </midColor></colorRanges>

As shown in Table 2, if the sum of the EXP_AMOUNT column is higher than5,000, the cell containing the sum value may be highlighted using afirst combination of red, green and blue color values. If the sum isless than 100, the cell containing the sum value may be highlightedusing a second combination of red, green and blue color values. If thesum is between 100 and 5,000, the cell containing the sum value may behighlighted using a third combination of red, green and blue colorvalues.

Table 3 illustrates another example of a report programmatically definedutilizing an XML schema. Again, it should be noted that the report isset forth for illustrative purposes only, and thus should not beconstrued as limiting in any manner.

TABLE 3 <?xml version=“1.0” encoding=“UTF-8”?> <CustomReportxmlns=“http://soap.sforce.com/2006/04/metadata”> <chartXAxisColumn>INDUSTRY</chartXAxisColumn> <chartYAxisColumn>CLOSE_MONTH</chartYAxisColumn>  <colorRanges>  <aggregate>Sum</aggregate>   <columnName>EXP_AMOUNT</columnName>  <highBreakpoint>5000.0</highBreakpoint>   <highColor>   <blue>84</blue>    <green>194</green>    <red>84</red>   </highColor>  <lowBreakpoint>100.0</lowBreakpoint>   <lowColor>    <blue>0</blue>   <green>204</green>    <red>51</red>   </lowColor>   <midColor>   <blue>84</blue>    <green>194</green>    <red>194</red>   </midColor> </colorRanges>  <columns>   <field>FULL_NAME</field>  </columns> <columns>   <field>OPPORTUNITY_NAME</field>  </columns>  <columns>  <field>TYPE</field>  </columns>  <columns>  <field>LEAD_SOURCE</field>  </columns>  <columns>  <field>AMOUNT</field>  </columns>  <columns>  <field>EXP_AMOUNT</field>  </columns>  <columns>  <field>CLOSE_DATE</field>  </columns>  <columns>  <field>NEXT_STEP</field>  </columns>  <columns>  <field>STAGE_NAME</field>  </columns>  <columns>   <field>AGE</field> </columns>  <columns>   <field>ROLLUP_DESCRIPTION</field>  </columns> <columns>   <field>CREATED...DATE</field>  </columns>  <columns>  <field>ACCOUNT_NAME</field>  </columns>  <division>null</division> <filters>   <column>AGE</column>   <operator>greaterThan</operator>  <value>0</value>  </filters>  <format>Matrix</format>  <params>  <name>quarter</name>   <value>custom</value>  </params>  <params>  <name>scope</name>   <value>organization</value>  </params>  <params>  <name>open</name>   <value>all</value>  </params>  <params>  <name>probability</name>   <valup>&gt;0</value>  </params>  <params>  <name>div_rep</name>   <value></value>  </params>

Further, if it is determined that the report is received, the report isstored using the multi-tenant on-demand database service. See operation204. For example, the report may be stored in a database of themulti-tenant on-demand database service.

In an embodiment where the report is defined programmatically, thereport may be received from a metadata API which interacts directly witha report interface of the multi-tenant on-demand database service. Forexample, the metadata API may include a deploy method to write thereport to the report interface. In an embodiment where the report isdefined via the user interface of the multi-tenant on-demand databaseservice, the report may be received from the user interface whichinteracts directly with the report interface of the multi-tenanton-demand database service. For example, the user interface may includea deploy method (e.g. identical to the deploy method of the metadataAPI) to write the report to the report interface.

In one embodiment, the report may be stored utilizing a metadata schemathat is accessible by each tenant of the multi-tenant on-demand databaseservice. Thus, if the report is defined programmatically in suchmetadata schema format, then the report may be directly stored withoutprocessing. If, however, the report is defined via the user interface,the report may be converted from a format used by the user interface tothe metadata schema, such that the report is stored in the metadataschema.

Once the report is stored, it is determined whether a request for thereport is received from a second tenant of the multi-tenant on-demanddatabase service. See decision 206. The second tenant may include anytenant that is different from the first tenant. The request may be toview the report, modify the report, purchase the report, etc.

If it is determined that a request for the report is not received from asecond tenant of the multi-tenant on-demand database service, the method200 continues to wait for such a request to be received. If it isdetermined that a request for the report is received from a secondtenant of the multi-tenant on-demand database service, the report isprovided to the second tenant. See operation 208. In one embodiment, thereport may be provided utilizing a package sent to the second tenant. Ofcourse, however, the report may be provided in any desired manner (e.g.for the second tenant to view the report, modify the report, etc.).

For example, if the report is requested via the metadata API describedabove (e.g. for viewing programmatically), a retrieve method of themetadata API may read the report from the multi-tenant on-demanddatabase service. If the report is requested via the user interface(e.g. for viewing in the user interface), a retrieve method of the userinterface (e.g. identical to the retrieve method of the metadata API)may read the report from the multi-tenant on-demand database service.

If the report is validated at runtime, as described above, the runtimedefinition of the report may differ from the stored definition of thereport. For example, the set of columns available to the second tenantmay be based on permissions, etc. which may change over time.Additionally, available fields may also change over time (e.g. may bedeleted, etc.). If the report is provided via the user interface, thereport is allowed to run without data (e.g. columns) that isunavailable. Thus, for example, if a filter or grouping requires anunavailable column, the report is run without the filter/grouping. Inanother exemplary embodiment, if a matrix report is grouped by industryand the industry field is not available to the second tenant, the reportmay be run without the industry grouping and, optionally, the report maybe converted into a summary report rather than a matrix report (toeliminate errors resulting from the removal of the industry grouping).

FIG. 3 shows a user interface 300 for configuring filters for a report,in accordance with yet another embodiment. As an option, the userinterface 300 may be implemented in the context of the functionality ofFIGS. 1-2. Of course, however, the user interface 300 may be implementedin any desired environment. Again, the aforementioned definitions mayapply during the present description.

As shown, the user interface 300 allows a first tenant of a multi-tenanton-demand database service to configure multiple filters for a report.The filters may each be configured via a filter item. The filter itemincludes a field input field for selecting (e.g. from a drop-down list)a field of a table, an operator field for selecting an operator to beapplied to the field of the table, and a value field for specifying avalue against which the field is to be applied using the operator.Additionally, Boolean conditions may be defined between the filter itemsfor specifying a manner in which the filters are to be applied.

FIG. 4 shows a user interface 400 for grouping reports, in accordancewith still yet another embodiment. As an option, the user interface 400may be implemented in the context of the functionality of FIGS. 1-2. Ofcourse, however, the user interface 400 may be implemented in anydesired environment. Again, the aforementioned definitions may applyduring the present description.

As shown, the user interface 400 allows a first tenant of a multi-tenanton-demand database service to configure groupings for a report. Thegroupings may be used to group columns and/or rows being reported viathe report. Thus, the groupings may group data for being summarized inthe report.

System Overview

FIG. 5 illustrates a block diagram of an environment 510 wherein anon-demand database service might be used. As an option, any of thepreviously described embodiments of the foregoing figures may or may notbe implemented in the context of the environment 510. Environment 510may include user systems 512, network 514, system 516, processor system517, application platform 518, network interface 520, tenant datastorage 522, system data storage 524, program code 526, and processspace 528. In other embodiments, environment 510 may not have all of thecomponents listed and/or may have other elements instead of, or inaddition to, those listed above.

Environment 510 is an environment in which an on-demand database serviceexists. User system 512 may be any machine or system that is used by auser to access a database user system. For example, any of user systems512 can be a handheld computing device, a mobile phone, a laptopcomputer, a work station, and/or a network of computing devices. Asillustrated in FIG. 5 (and in more detail in FIG. 6) user systems 512might interact via a network with an on-demand database service, whichis system 516.

An on-demand database service, such as system 516, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databaseservices may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS). Accordingly, “on-demand database service 516” and “system 516”will be used interchangeably herein. A database image may include one ormore database objects. A relational database management system (RDMS) orthe equivalent may execute storage and retrieval of information againstthe database object(s). Application platform 518 may be a framework thatallows the applications of system 516 to run, such as the hardwareand/or software, e.g., the operating system. In an embodiment, on-demanddatabase service 516 may include an application platform 518 thatenables creation, managing and executing one or more applicationsdeveloped by the provider of the on-demand database service, usersaccessing the on-demand database service via user systems 512, or thirdparty application developers accessing the on-demand database servicevia user systems 512.

The users of user systems 512 may differ in their respective capacities,and the capacity of a particular user system 512 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a salesperson is using a particular user system 512 tointeract with system 516, that user system has the capacities allottedto that salesperson. However, while an administrator is using that usersystem to interact with system 516, that user system has the capacitiesallotted to that administrator. In systems with a hierarchical rolemodel, users at one permission level may have access to applications,data, and database information accessible by a lower permission leveluser, but may not have access to certain applications, databaseinformation, and data accessible by a user at a higher permission level.Thus, different users will have different capabilities with regard toaccessing and modifying application and database information, dependingon a user's security or permission level.

Network 514 is any network or combination of networks of devices thatcommunicate with one another. For example, network 514 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network, such as the global internetwork of networks often referred toas the “Internet” with a capital “I,” that network will be used in manyof the examples herein. However, it should be understood that thenetworks that the present invention might use are not so limited,although TCP/IP is a frequently implemented protocol.

User systems 512 might communicate with system 516 using TCP/IP and, ata higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 512 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 516. Such an HTTP server might be implemented asthe sole network interface between system 516 and network 514, but othertechniques might be used as well or instead. In some implementations,the interface between system 516 and network 514 includes load sharingfunctionality, such as round-robin HTTP request distributors to balanceloads and distribute incoming HTTP requests evenly over a plurality ofservers. At least as for the users that are accessing that server, eachof the plurality of servers has access to the MTS' data; however, otheralternative configurations may be used instead.

In one embodiment, system 516, shown in FIG. 5, implements a web-basedcustomer relationship management (CRM) system. For example, in oneembodiment, system 516 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, webpages and other information to and fromuser systems 512 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject, however, tenant data typically is arranged so that data of onetenant is kept logically separate from that of other tenants so that onetenant does not have access to another tenant's data, unless such datais expressly shared. In certain embodiments, system 516 implementsapplications other than, or in addition to, a CRM application. Forexample, system 516 may provide tenant access to multiple hosted(standard and custom) applications, including a CRM application. User(or third party developer) applications, which may or may not includeCRM, may be supported by the application platform 518, which managescreation, storage of the applications into one or more database objectsand executing of the applications in a virtual machine in the processspace of the system 516.

One arrangement for elements of system 516 is shown in FIG. 6, includinga network interface 520, application platform 518, tenant data storage522 for tenant data 523, system data storage 524 for system dataaccessible to system 516 and possibly multiple tenants, program code 526for implementing various functions of system 516, and a process space528 for executing MTS system processes and tenant-specific processes,such as running applications as part of an application hosting service.Additional processes that may execute on system 516 include databaseindexing processes.

Several elements in the system shown in FIG. 5 include conventional,well-known elements that are explained only briefly here. For example,each user system 512 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 512 typically runs an HTTP client, e.g., abrowsing program, such as Microsoft's Internet Explorer browser,Netscape's Navigator browser, Opera's browser, or a WAP-enabled browserin the case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g. subscriber of the multi-tenant database system) ofuser system 512 to access, process and view information, pages andapplications available to it from system 516 over network 514. Each usersystem 512 also typically includes one or more user interface devices,such as a keyboard, a mouse, trackball, touch pad, touch screen, pen orthe like, for interacting with a graphical user interface (GUI) providedby the browser on a display (e.g. a monitor screen, LCD display, etc.)in conjunction with pages, forms, applications and other informationprovided by system 516 or other systems or servers. For example, theuser interface device can be used to access data and applications hostedby system 516, and to perform searches on stored data, and otherwiseallow a user to interact with various GUI pages that may be presented toa user. As discussed above, embodiments are suitable for use with theInternet, which refers to a specific global internetwork of networks.However, it should be understood that other networks can be used insteadof the Internet, such as an intranet, an extranet, a virtual privatenetwork (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 512 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor the like. Similarly, system 516 (andadditional instances of an MTS, where more than one is present) and allof their components might be operator configurable using application(s)including computer code to run using a central processing unit such asprocessor system 517 of FIG. 5, which may include an Intel Pentium®processor or the like, and/or multiple processor units. A computerprogram product embodiment includes a machine-readable storage medium(media) having instructions stored thereon/in which can be used toprogram a computer to perform any of the processes of the embodimentsdescribed herein. Computer code for operating and configuring system 516to communicate and to process webpages, applications and other data andmedia content as described herein are preferably downloaded and storedon a hard disk, but the entire program code, or portions thereof, mayalso be stored in any other non-transitory computer readable medium ordevice as is well known to include only hardware devices, such as a ROMor RAM, or provided on any other hardware device capable of storingprogram code, such as any type of rotating media including floppy disks,optical discs, digital versatile disk (DVD), compact disk (CD),microdrive, and magneto-optical disks, and magnetic or optical cards,nanosystems (including molecular memory ICs), or any type of hardwaredevice suitable for storing instructions and/or data. Additionally, theentire program code, or portions thereof, may be transmitted anddownloaded from a software source over a transmission medium, e.g., overthe Internet, or from another server, as is well known, or transmittedover any other conventional network connection as is well known (e.g.extranet, VPN, LAN, etc.) using any communication medium and protocols(e.g. TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It willalso be appreciated that computer code for implementing embodiments ofthe present invention can be implemented in any programming languagethat can be executed on a client system and/or server or server systemsuch as, for example, C, C++, HTML, any other markup language, Java™,JavaScript, ActiveX, any other scripting language, such as VBScript, andmany other programming languages as are well known may be used. (Java™is a trademark of Sun Microsystems, Inc.).

According to one embodiment, each system 516 is configured to providewebpages, forms, applications, data and media content to user (client)systems 512 to support the access by user systems 512 as tenants ofsystem 516. As such, system 516 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another (e.g.in a server farm located in a single building or campus), or they may bedistributed at locations remote from one another (e.g. one or moreservers located in city A and one or more servers located in city B). Asused herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant toinclude a computer system, including processing hardware and processspace(s), and an associated storage system and database application(e.g. OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database object described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 6 also illustrates environment 510. However, in FIG. 6 elements ofsystem 516 and various interconnections in an embodiment are furtherillustrated. FIG. 6 shows that user system 512 may include processorsystem 512A, memory system 512B, input system 512C, and output system512D. FIG. 6 shows network 514 and system 516. FIG. 6 also shows thatsystem 516 may include tenant data storage 522, tenant data 523, systemdata storage 524, system data 525, User Interface (UI) 630, ApplicationProgram Interface (API) 632, PL/SOQL 634, save routines 636, applicationsetup mechanism 638, applications servers 600 ₁-600 _(N), system processspace 602, tenant process spaces 604, tenant management process space610, tenant storage area 612, user storage 614, and application metadata616. In other embodiments, environment 510 may not have the sameelements as those listed above and/or may have other elements insteadof, or in addition to, those listed above.

User system 512, network 514, system 516, tenant data storage 522, andsystem data storage 524 were discussed above in FIG. 5. Regarding usersystem 512, processor system 512A may be any combination of one or moreprocessors. Memory system 512B may be any combination of one or morememory devices, short term, and/or long term memory. Input system 512Cmay be any combination of input devices, such as one or more keyboards,mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 512D may be any combination of output devices, such as oneor more monitors, printers, and/or interfaces to networks. As shown byFIG. 6, system 516 may include a network interface 520 (of FIG. 5)implemented as a set of HTTP application servers 600, an applicationplatform 518, tenant data storage 522, and system data storage 524. Alsoshown is system process space 602, including individual tenant processspaces 604 and a tenant management process space 610. Each applicationserver 600 may be configured to tenant data storage 522 and the tenantdata 523 therein, and system data storage 524 and the system data 525therein to serve requests of user systems 512. The tenant data 523 mightbe divided into individual tenant storage areas 612, which can be eithera physical arrangement and/or a logical arrangement of data. Within eachtenant storage area 612, user storage 614 and application metadata 616might be similarly allocated for each user. For example, a copy of auser's most recently used (MRU) items might be stored to user storage614. Similarly, a copy of MRU items for an entire organization that is atenant might be stored to tenant storage area 612. A UI 630 provides auser interface and an API 632 provides an application programmerinterface to system 516 resident processes to users and/or developers atuser systems 512. The tenant data and the system data may be stored invarious databases, such as one or more Oracle™ databases.

Application platform 518 includes an application setup mechanism 638that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage522 by save routines 636 for execution by subscribers as one or moretenant process spaces 604 managed by tenant management process 610 forexample. Invocations to such applications may be coded using PL/SOQL 634that provides a programming language style interface extension to API632. A detailed description of some PL/SOQL language embodiments isdiscussed in commonly owned U.S. Provisional Patent Application60/828,192 entitled, “PROGRAMMING LANGUAGE METHOD AND SYSTEM FOREXTENDING APIS TO EXECUTE IN CONJUNCTION WITH DATABASE APIS,” by CraigWeissman, filed Oct. 4, 2006, which is incorporated in its entiretyherein for all purposes. Invocations to applications may be detected byone or more system processes, which manage retrieving applicationmetadata 616 for the subscriber making the invocation and executing themetadata as an application in a virtual machine.

Each application server 600 may be communicably coupled to databasesystems, e.g., having access to system data 525 and tenant data 523, viaa different network connection. For example, one application server 600₁ might be coupled via the network 514 (e.g., the Internet), anotherapplication server 600 _(N-1) might be coupled via a direct networklink, and another application server 600 _(N) might be coupled by yet adifferent network connection. Transfer Control Protocol and InternetProtocol (TCP/IP) are typical protocols for communicating betweenapplication servers 600 and the database system. However, it will beapparent to one skilled in the art that other transport protocols may beused to optimize the system depending on the network interconnect used.

In certain embodiments, each application server 600 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 600.

In one embodiment, therefore, an interface system implementing a loadbalancing function (e.g., an F5 Big-IP load balancer) is communicablycoupled between the application servers 600 and the user systems 512 todistribute requests to the application servers 600. In one embodiment,the load balancer uses a least connections algorithm to route userrequests to the application servers 600. Other examples of loadbalancing algorithms, such as round robin and observed response time,also can be used. For example, in certain embodiments, three consecutiverequests from the same user could hit three different applicationservers 600, and three requests from different users could hit the sameapplication server 600. In this manner, system 516 is multi-tenant,wherein system 516 handles storage of, and access to, different objects,data and applications across disparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 516 to manage their salesprocess. Thus, a user might maintain contact data, leads data, customerfollow-up data, performance data, goals and progress data, etc., allapplicable to that user's personal sales process (e.g., in tenant datastorage 522). In an example of a MTS arrangement, since all of the dataand the applications to access, view, modify, report, transmit,calculate, etc., can be maintained and accessed by a user system havingnothing more than network access, the user can manage his or her salesefforts and cycles from any of many different user systems. For example,if a salesperson is visiting a customer and the customer has Internetaccess in their lobby, the salesperson can obtain critical updates as tothat customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 516 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant-specific data, system 516 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain embodiments, user systems 512 (which may be client systems)communicate with application servers 600 to request and updatesystem-level and tenant-level data from system 516 that may requiresending one or more queries to tenant data storage 522 and/or systemdata storage 524. System 516 (e.g., an application server 600 in system516) automatically generates one or more SQL statements (e.g., one ormore SQL queries) that are designed to access the desired information.System data storage 524 may generate query plans to access the requesteddata from the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects according to the present invention. It should be understood that“table” and “object” may be used interchangeably herein. Each tablegenerally contains one or more data categories logically arranged ascolumns or fields in a viewable schema. Each row or record of a tablecontains an instance of data for each category defined by the fields.For example, a CRM database may include a table that describes acustomer with fields for basic contact information such as name,address, phone number, fax number, etc. Another table might describe apurchase order, including fields for information such as customer,product, sale price, date, etc. In some multi-tenant database systems,standard entity tables might be provided for use by all tenants. For CRMdatabase applications, such standard entities might include tables forAccount, Contact, Lead, and Opportunity data, each containingpre-defined fields. It should be understood that the word “entity” mayalso be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. U.S. patent application Ser. No.10/817,161, filed Apr. 2, 2004, entitled “CUSTOM ENTITIES AND FIELDS INA MULTI-TENANT DATABASE SYSTEM,” which is hereby incorporated herein byreference, teaches systems and methods for creating custom objects aswell as customizing standard objects in a multi-tenant database system.In certain embodiments, for example, all custom entity data rows arestored in a single multi-tenant physical table, which may containmultiple logical tables per organization. It is transparent to customersthat their multiple “tables” are in fact stored in one large table orthat their data may be stored in the same table as the data of othercustomers.

It should be noted that any of the different embodiments describedherein may or may not be equipped with any one or more of the featuresset forth in one or more of the following published applications:US2003/0233404, titled “OFFLINE SIMULATION OF ONLINE SESSION BETWEENCLIENT AND SERVER,” filed Nov. 4, 2002; US2004/0210909, titled “JAVAOBJECT CACHE SERVER FOR DATABASES,” filed Apr. 17, 2003, now issued U.S.Pat. No. 7,209,929; US2005/0065925, titled “QUERY OPTIMIZATION IN AMULTI-TENANT DATABASE SYSTEM,” filed Sep. 23, 2003; US2005/0223022,titled “CUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASE SYSTEM,”filed Apr. 2, 2004; US2005/0283478, titled “SOAP-BASED WEB SERVICES IN AMULTI-TENANT DATABASE SYSTEM,” filed Jun. 16, 2004; US2006/0206834,titled “SYSTEMS AND METHODS FOR IMPLEMENTING MULTI-APPLICATION TABS ANDTAB SETS,” filed Mar. 8, 2005; US2008/0010243, titled “METHOD AND SYSTEMFOR PUSHING DATA TO A PLURALITY OF DEVICES IN AN ON-DEMAND SERVICEENVIRONMENT,” filed Jun. 1, 2007; and/or US 2009/0037828 titled “SYSTEM,METHOD AND COMPUTER PROGRAM PRODUCT FOR EDITING AN ON-DEMAND DATABASESERVICE GRAPHICAL USER INTERFACE,” filed Jul. 17, 2008, which are eachincorporated herein by reference in their entirety for all purposes.

While the invention has been described by way of example and in terms ofthe specific embodiments, it is to be understood that the invention isnot limited to the disclosed embodiments. To the contrary, it isintended to cover various modifications and similar arrangements aswould be apparent to those skilled in the art. Therefore, the scope ofthe appended claims should be accorded the broadest interpretation so asto encompass all such modifications and similar arrangements.

The invention claimed is:
 1. A method, comprising: receiving at amulti-tenant on-demand database service a report from a first tenant ofthe multi-tenant on-demand database service, wherein the report receivedfrom the first tenant defines a scope of the report to indicate a subsetof data in a particular database of the multi-tenant on-demand databaseservice being reported via the report; and storing the report in adatabase of the multi-tenant on-demand database service for use by atleast one second tenant of the multi-tenant on-demand database service;wherein the multi-tenant on-demand database service includes a databasesystem accessible to the first tenant and the at least one second tenantover a network, which has hardware and software that is shared by boththe first tenant and the at least one second tenant, which stores datafor each of the first tenant and the at least one second tenant in alogically separate manner, and which processes requests for the firsttenant with respect to at least the data stored for the first tenant andprocesses requests for the at least one second tenant with respect to atleast the data stored for the at least one second tenant.
 2. The methodof claim 1, wherein the report includes a plurality of portions definedby the first tenant.
 3. The method of claim 2, wherein the portionsinclude at least one of columns, filters, formulas, parameters, andcolor ranges.
 4. The method of claim 2, wherein the defined portionsinclude columns, filters, formulas, parameters, and color ranges.
 5. Themethod of claim 2, wherein the portions are defined by the first tenantutilizing a user interface of the multi-tenant on-demand databaseservice.
 6. The method of claim 2, wherein the portions are definedprogrammatically by the first tenant utilizing a metadata schema.
 7. Themethod of claim 6, wherein the metadata schema includes an extensiblemarkup language (XML) schema.
 8. The method of claim 1, wherein thereport is received by the multi-tenant on-demand database serviceutilizing an application program interface of the multi-tenant on-demanddatabase service.
 9. The method of claim 1, wherein the scope of thereport indicates that data of the at least one second tenant in thedatabase is being reported via the report.
 10. The method of claim 1,wherein in response to a request for the report received by themulti-tenant on-demand database service from the at least one secondtenant, the report is run without data that is unavailable to the atleast one second tenant as determined by permissions defined for the atleast one second tenant, such that a runtime definition of the reportdiffers from a stored definition of the report.
 11. The method of claim6, wherein the report is stored in the metadata schema.
 12. The methodof claim 5, wherein the report is converted from a format associatedwith the user interface to a metadata schema for storing the report inthe metadata schema.
 13. The method of claim 1, wherein the report isstored in a format accessible to the first tenant and the at least onesecond tenant.
 14. The method of claim 1, wherein the at least onesecond tenant is different from the first tenant.
 15. The method ofclaim 1, wherein the use by the at least one second tenant includesviewing the report.
 16. The method of claim 1, wherein the use by the atleast one second tenant includes modifying the report.
 17. The method ofclaim 1, further comprising receiving a request for the report by the atleast one second tenant.
 18. The method of claim 17, further comprisingproviding the report to the at least one second tenant via anapplication program interface of the multi-tenant on-demand databaseservice.
 19. A computer program product embodied on a non-transitorycomputer readable medium, comprising: computer code for receiving at amulti-tenant on-demand database service a report from a first tenant ofthe multi-tenant on-demand database service, wherein the report receivedfrom the first tenant defines a scope of the report to indicate a subsetof data in a particular database of the multi-tenant on-demand databaseservice being reported via the report; and computer code for storing thereport in a database of the multi-tenant on-demand database service foruse by at least one second tenant of the multi-tenant on-demand databaseservice; wherein the multi-tenant on-demand database service includes adatabase system accessible to the first tenant and the at least onesecond tenant over a network, which has hardware and software that isshared by both the first tenant and the at least one second tenant,which stores data for each of the first tenant and the at least onesecond tenant in a logically separate manner, and which processesrequests for the first tenant with respect to at least the data storedfor the first tenant and processes requests for the at least one secondtenant with respect to at least the data stored for the at least onesecond tenant.
 20. An apparatus, comprising: a processor for: receivingat a multi-tenant on-demand database service a report from a firsttenant of the multi-tenant on-demand database service, wherein thereport received from the first tenant defines a scope of the report toindicate a subset of data in a particular database of the multi-tenanton-demand database service being reported via the report; and storingthe report in a database of the multi-tenant on-demand database servicefor use by at least one second tenant of the multi-tenant on-demanddatabase service; wherein the multi-tenant on-demand database serviceincludes a database system accessible to the first tenant and the atleast one second tenant over a network, which has hardware and softwarethat is shared by both the first tenant and the at least one secondtenant, which stores data for each of the first tenant and the at leastone second tenant in a logically separate manner, and which processesrequests for the first tenant with respect to at least the data storedfor the first tenant and processes requests for the at least one secondtenant with respect to at least the data stored for the at least onesecond tenant.
 21. The apparatus of claim 20, wherein the processor iscoupled to memory via a bus.